View ATAVRDRAGON_7393839.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

introduction page 1 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 introducing avr dragon ' front side back side with the avr dragon , atmel has set a new standard for low cost develop ment tools. avr dragon supports all programming modes for the atmel avr device family. it also include full emulation support for devices with 32kb or les s flash memory. at a fraction of the price traditionally associated with this kind of featured tool, the avr dragon will fulfill all your programming and emulat ion needs. the flexible and secure firmware upgrade feature allows avr studio to easil y upgrade the avr dragon to support new devices. to see which devices are currently supported please read the device support page. (new devices will be added through avr studio updat es or service packs on a regular basis) supported protocols currently the following protocols are supported: programming interfaces : in system programming ( isp ) high voltage serial programming ( hvsp ) parallel programming ( pp )
introduction page 2 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 jtag programming ( jtag prog ) emulation interfaces: (only available for devices with 32kb flash or les s) jtag ( jtag ) debugwire ( dw ) avr dragon can be used with an external target boar d. however, the onboard prototype area, allow simple programming and debugging withou t any additional hardware. please see the using the avr prototype area section for a description on how to use this. avr dragon is powered by the usb cable, and can als o source an external target with up to 300ma (from the vcc connector) when programming or debugging. for more information on technical details, please read the avr dragon requirements section. if the target is already powered by an external power sour ce, the avr dragon will adapt and level convert all signals between the target and th e avr dragon. note: it the target board is powered by external power s ource, no connection should be made betwwen the vcc connector and the external boa rd. avr dragon if fully supported by avr studio. this a llows the avr dragon firmware to be easily updated to support new devices and protocols . when connecting the avr dragon, avr studio will automatically check the firmware an d prompt the user if an updated firmware is available. device support the following devices are currently supported by av r dragon. programming emulation device isp hvsp pp* jtag jtag dw remarks atmega48/88/168 x x x atmega8 x x atmega8 does not have on-chip debug function atmega16 x x x x atmega169 x x x x off board target atmega32 x x x x atmega325p atmega3250p atmega329p atmega3290p x x x x off board target
introduction page 3 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 *note that pp/hvsp (parallel and high voltage seria l programming) is not recommended to use off board the avr dragon. pp/hvsp signals ar e not level converted on the avr dragon. new devices will be supported through updates of av r studio. please visit www.atmel.com to download the latest version. what's new september 18th, 2006 - sw: 0x0101 0x0103 fixed problem with programming more than 10 bytes o f data to eeprom in debugwire mode fixed problems with reading and storing isp program ming frequence fixed that pp/hvsp is automatically selected as pro gramming interface if it was used last time. fixed usb reenumeration issue, caused when disconne ct/connecting the avr dragon when target voltage is below 1.8v, the avr dragon n ow reports the actual voltage, not only "could not find target voltage" august 3rd, 2006 - sw: 0x0100 0x0102 full support for: atmega16, atmega169, atmega325p, atmega3250p, atmega329p and atmega3290p june 29, 2006 - avr studio 4.12 sp3: sw: 0x0100 0x0 102 fixed bug causing slow isp programming june 12, 2006 - avr studio 4.12 sp3: sw: 0x0100 0x0 101 full support for: atmega48/88/168, atmega8, atmega 32, atmega128, attiny13, attiny25/45/85 and attiny2313 getting started atmega128 x x x no emulation support for devices > 32k flash off board target attiny13 x x x attiny25/45/85 x x x attiny2313 x x x
introduction page 4 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 please read this section before connecting the avr dragon to the computer or target. follow these simple steps to get started using the avr dragon: 1. download avr studio 4.12 sp3 or later from http:/ /www.atmel.com/avrdragon 2. install avr studio and the usb driver 3. connect avr dragon to the computer, and auto-inst all new hardware (avr dragon) on the computer 4. start avr studio and the avr dragon programming d ialog 5. connect avr dragon to the target usb setup in order to use the avr dragon it is required to in stall the avr studio and usb driver first. please do not connect the avr dragon to the compute r before running the usb setup in order to follow this procedure described in softwar e and usb setup. unpacking the avr dragon. the box contains: avr dragon tool internet link to software ( http://www.atmel.com/av rdragon ) there is no cd shipped with the avr dragon. the onl y way of getting the software is by downloading it directly from the internet. you will also need: (not included) pc with free usb connector or a usb hub capable of delivering 500ma usb cable avr studio 4.12 with service pack 3 or later ( link : http://www.atmel.com/avrdragon ) 6/10 pin header connector (or similar cables to con nect the avr dragon to the target board) system requirements the minimum hardware and software requirements are: 1. pentium (pentium ii and above is recommended) 2. windows? 98, windows me, windows? 2000 or windows ? xp 3. 64 mb ram 4. avr studio 4.12 with service pack 3 5. usb port, self-powered (500ma required) 6. internet connection for software download important ! please install avr studio and the usb driver before connecting avr dragon to your pc
introduction page 5 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 note: windows 95 and windows nt does not support usb, he nce cannot be used with avr dragon software and usb setup software and usb setup in order to use the avr dragon it is required to in stall the usb driver. please do not connect the avr dragon to the computer before runni ng the usb setup. usb driver installation is done during the avr studio installa tion. note : avr dragon requires avr studio 4.12 with service pack 3 or later. latest version of the avr studio can be found at: www.atmel.com/produ cts/avr/ start the avr studio installation. during this inst allation the dialog box in the figure below will be presented to the user.
introduction page 6 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 to install the usb driver, check the install/upgrad e usb driver checkbox, and the usb driver will automatically be installed. install new hardware on the computer when avr studio and usb driver installation is fini shed, please attach the usb cable to both pc and avr dragon. (the avr dragon is powered from the usb). if it is the first time the avr dragon is connected to the computer, the bo x below will appear: if running windows xp you need to click "next" a co uple of times. please wait until the installation process completes by itself. it may ta ke from a few seconds up to a few minutes depending on the computer and operating system. if the usb driver is correctly installed and avr dr agon is connect to the pc, the green led inside the encasing next to the usb connector will be lit. if the avr studio for some reason can't detect the avr dragon after the usb setup, try to restart the computer in order to get the driver pro perly loaded. install usb driver after avr studio is installed the usb driver can be installed even after avr stud io have been installed by following these steps: 1. open "control panel" on the pc (windows 95 and wi ndows nt does not support
introduction page 7 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 usb) 2. select "add or remove programs" 3. select "avrstudio4" in the list of programs 4. click on the "change" button 5. select "modify" 6. select "install/upgrade usb driver" the usb driver is now properly installed on the pc note : the avr dragon requires a usb port that can deliv er 500ma (self-powered usb hub). board description avr dragon board: headers: out of the box, the avr dragon has the following 3 header connectors mounted: isp header - used for isp programming and debugwire ocd
introduction page 8 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 jtag header - used for jtag programming and jtag oc d. vcc header - used for powering devices placed in th e prototype area, or to power external target boards (max 300ma) the following header are not mounted hv_prog header expand header 40-pin dip socket 28-pin dip socket isp header (mounted): this 6-pin header uses the standard avr isp pinout for easy connection to external targets. the signals are level-converted to allow c ommunication with targets running at any voltage between 1.8 and 5.5v jtag header(mounted): the 10-pin jtag header is a standard pinout jtag co nnector. when connecting the avr dragon jtag header to an external target, the signa ls are level converted to match the target board voltage. this is done automatically. p lease note that the avr dragon will not power the target through the jtag interface. the ta rget needs to be powered through a dedicated powersupply. (or by powering it using the vcc connector (5.0v max 300ma) hv_prog header (not mounted): pin signal i/o description 1 tck output test clock, clock signal from avr dragon to target jtag port 2 gnd - ground 3 tdo input test data output, data signal from target jtag port to avr dragon 4 vtref input target reference voltage. vdd from target used to control level-converter 5 tms output test mode select, mode select signal from avr dragon to target jtag port 6 nsrst in/out- put open collector output from adapter to the target sy stem reset. this pin is also an input to the adapter so that the reset initiated on the target may be reported t o the avr dragon 7 - - not connected 8 ntrst nc (output) not connected, reserved for compatibility with othe r equipment (jtag port reset) 9 tdi output test data input, data signal from avr dragoi to tar get jtag port 10 gnd - ground
introduction page 9 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 the hv_prog connector contains all signal required to do hvsp or pp programming. the signals on this connector is not level-converted, a nd should only be connected to the expand connector on the avr dragon. you could damag e both your target and the avr dragon if you try to do hvsp or pp on an external t arget board. vcc header (mounted): the vcc header contains 5.0 volt vcc and gnd that m ust be used to power the target device placed in the prototype area of the avr drag on board. the voltage can also be used to power an external target board, but it is i mportant that the current consumption is less than 300ma. please note that the avr dragon cu rrent sourcing capabilities are also limited by the amount of current the host usb contr oller can deliver. expand header (not mounted): the expand connector is directly mapped to the 28 a nd 40-pin dip sockets. pin 1 on the connector - is pin one on both the 28 and the 40pin dip socket. when doing either programming or emulation on-board, the appropriate signals should be routed from the isp, jtag, vcc and hv_prog headers to the correct pins o n the expand connector. please read the " using the avr dragon prototype area " section for more information on how to use this function.
introduction page 10 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 status leds two leds show the status of the avr dragon. check t he troubleshooting guide to check for solutions if there are any errors. in system programming in system programming is well suited for programmin g devices soldered onto external target boards. this section explains how to connect the avr dragon to isp program an external target. the isp lines are equipped with le vel converters that automatically will level shift the avr dragon to the target board volt age. it is recommended that a 6-pin header connector wit h 2.54mm (100 mil) spacing is placed on the target board to allow easy access to the isp programming interface. the following led # color description 2 green indicates usb traffic 1 red idle, not connected to avr studio dark idle, connected to avr studio green data transfere yellow firmware upgrade or initialization
introduction page 11 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 pinout should be used. figure: 6pin header connector with 2.54mm (100 mil) spacing note : when connecting the avr dragon to the target, con nect miso to miso pin on the target device, mosi to mosi and so on. connect the 6pin cable from the avr dragon to the e xternal target as shown in these pictures: debugwire ocd interface is also accessed through th is isp header. high voltage serial programming description low pin count avr devices do not have enough io pin s to support the full parallel programming interface. these devices instead use hv sp programming, which is a serial version of the parallel programming interface. important! extreme care should be taken if using hvsp mode to program a avr device on an external target. the hvsp lines do not have level converters , so it is important that the target board is powered by the avr dragon vcc header, and not using another power supply. in addition the avr dragon will apply 12v to the reset pin, so it is important that the target board is designed to handle 12v on this line. to avoid damaging the target board, the avr dragon or both, it is recommended to only use hvsp mode on devices placed in the 28/40 pin di p socket on the avr prototyp area on the avr dragon.
introduction page 12 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 please see the "device connection sheet" section fo r information on how to connect avr dragon for hvsp programming for the different suppo rted devices. figure: prototype area parallel programming description high pin count avr devices support the full parall el programming (pp) interface. this interface offer high speed programming, and also su pport programming all fuse and lock bits in the avr device. important! extreme care should be taken if using pp mode to pr ogram a avr device on an external target. the pp lines do not have level converters, so it is important that the target board then is powered by the avr dragon vcc header, and n ot using its own power supply. in addition the avr dragon will apply 12v to the reset pin, so it is important that the target board is designed to handle 12v on this line. to avoid damaging the target board, the avr dragon or both, it is recommended to only use pp mode on devices placed in the 28/40 pin dip socket on the avr prototyp area on the avr dragon. please see the "device connection sheet" section fo r information on how to connect avr dragon for pp programming. figure: prototype area
introduction page 13 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 jtag programming description avr devices with jtag interface also support progra mming through this interface. the connection for jtag programming is the same same as the jtag debug interface. please see section " connecting to target through the jtag interface " for information how to connect the avr dragon to your external target boar d. it is also possible to do jtag programming on a dev ice placed on the prototype area of the avr dragon. please see the "device connection s heets" for information on how to connect the different avr devices. connecting to the target through the jtag interface a minimum of 6 wires is required to connect avr dra gon to the target board. these signals are tck, tdo, tdi, tms, vtref and gnd. optional line is the nsrst. the ntrst signal is not used, and is reserved for compatibility with other equipment. nsrst is used to control and monitor the target res et line. this is however not necessary for correct emulation. but if the application code sets the jtd bit in the mcucsr, the jtag interface will be disabled. for the avr dragon to reprogram the target avr, it will need to have control of the reset pin. note: vsupply is not connected on the avr dragon. hence t he avr dragon cannot be powered from the target application. the following text and descriptions will assume a 6 -wire connection between the target and avr dragon.
introduction page 14 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 the figure below shows which jtag lines should be c onnected to the target avr to ensure correct operation. to avoid drive contention on the lines it is recommended that series resistors are placed between the jtag lines and ext ernal circuitry. the value of the resistor should be chosen so that the external circ uitry and the avr do not exceed their maximum ratings (i.e. sinks or sources to much curr ent). connecting avr dragon to target board connecting avr dragon to several devices placed in a jtag chain avr dragon support emulation of devices placed in a jtag chain. when connecting n devices in a jtag scan chain all devices should con nect to tms and tck in parallel. the first device should connects it's tdi to the emulat or while the tdo should be wired to tdi of the next device up to device n. the last device should connects it's tdo to the emulator. connecting avr dragon to stk500 stk500 does not have a dedicated jtag interface con nector. to connect the avr dragon to the stk500 board, the jtag probe must be strappe d to the appropriate jtag port pins of the target device using a squid cable. check the target device datasheet for the location of the jtag pins on the appropriate device. figure below shows an example on how the pins should be connected for an atmega32 on the stk 500. remember to remove the reset jumper on the stk500 if the reset pin is goin g to be controlled from the avr dragon. note: add-on cards for the stk500 like e.g. stk501/502 m ay have a dedicated jtag connector. example: connecting avr dragon to stk500 with atmeg a32 stk500 jtag adapter
introduction page 15 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 the stk500 jtag adapter, that comes with the jtagic e mkii, can be used to simplify the connection to the stk500 for avr devices with jtag that mates with socket sckt3100a3 and sckt3000d3 on the stk500. connecting through isp if the jtagen fuse (jtag enable) in the target devi ce is un-programmed, the jtag interface will be disabled. this fuse cannot be pro grammed through the jtag interface and must therefore be programmed through e.g. the isp i nterface. this can be done from the avr dragon by using the isp connector. note: if using this isp connection from avr dragon on a s tk500, be sure to de-attach the reset jumper on the stk500. and connect to the corr ect isp header. connecting to target through the debugwire interface a minimum of 3 wires is required for communication between avr dragon and the target board with the debugwire interface. these signals a re reset, vtref and gnd. important! this interface uses only 1 pin, (reset pin) for com munication with the target. to enable the debugwire interface on an avr device, the debug wire enable fuse (dwen) must be programmed, (dwen=0). avr devices with debugwire interface are shipped with the dwen fuse un-programmed from the factory. the debug wire interface itself cannot enable this fuse. the dwen fuse can be programmed t hrough isp mode, which requires connection to a 6-pin header. for this reason it is recommended to place the full 6-pin isp connector on your target board to simplify emulatio n and programming. note: when the dwen fuse is set, the isp interface normal functionality is disabled. this because the debugwire must have control over the re set pin. when dwen is set it is
introduction page 16 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 no longer possible to use isp. use debugwire or hig h voltage programming to disable the dwen fuse. note if using this connection from avr dragon on a stk5 00, be sure to de-attach the reset jumper on the stk500. and connect to the correct i sp header for the actual avr device, guided by the colour code in the stk500 silk-print. avr dragon debugwire connector connecting avr dragon probe to 6-pins isp header us ing a 6-pin cable when dwen fuse is programmed, there is only need fo r gnd, vtref and reset line for using the debugwire interface. however to ease the task of changing between isp mode and debugwire mode, it is recommended to do debugwi re with all six lines connected. the avr dragon will automatically tristate all unus ed isp pins when running debugwire. note: some precautions regarding the reset line must be t aken to ensure proper communication over the debugwire interface. if ther e is a pull-up on the reset line, this resistor must be larger than 10kohm, and there shou ld be no capacitive load. the pull-up resistor is not required for debugwire functionalit y. other logic connected to the reset line should be removed. note it's not possible to use the debugwire interface if the lockbits on the target avr are programmed. always be sure that the lockbits are cl eared before programming the dwen fuse and never set the lockbits while the dwen fuse is programmed. if both the debugwire enable fuse (dwen) and lockbits are set, one can use high voltage programming to do a chip erase, hence clear the loc kbits. when the lockbits are cleared the debugwire interface will be re-enabled. note the isp interface is only capable of reading fuses, signature and do a chip erase when the dwen fuse is unprogrammed.
introduction page 17 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 using the onboard prototype area the avr dragon has layout for a 40-pin and a 28-pin pdip socket. the dip socket pins are connected directly to the 40-pin header connect or. by strapping the isp, jtag, hv_prog and vcc header signals to the 40-pin header connector programming or emulation can be preformed without the need for an external target board. this section shows how to strap the avr dragon for different operation modes. each supported avr device has its own device connection sheet containing all information required. there is a number of ways to utilize the prototype area. if only one device type / programming mode is to be used, the easiest and che apest way is to just solder wires directly from the hv_prog, isp, jtag and vcc header s to the expand header. howerver, to make the board more flexible header co nnectors can be soldered in to allow using cables to be connected without soldering. here is a suggestion how to modify the avr dragon b oard to make it flexible and able to use all dip socket avr devices.
introduction page 18 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 in this picture one 20-pin header connector, a 40-p in header connector and a 40-pin dip socket has been soldered onto the avr dragon. to make it even more flexible and allow for narrow dip packages, a zif (zero insertion force) dip socket has been added in the picture abo ve. additional sockets can be bought from third party vendors to support mlf/qfn, tqfp, soic etc packages. (link: http://www.atmel.com/products/avr/thirdparty.asp#ad apters )
introduction page 19 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 - and finally the complete setup for debugwire and isp programming of the attiny45. for details on how this is connected please have a look at the attiny45 device connection sheet attiny13 devicesheet supported programming modes: isp, hvsp supported emulation modes: debugwire high voltage serial programming in system programming and debugwire emulation: vcc 6 a nc 5 4 nc nc 3 2 nc nc 1 hv_prog 20 h g 19 18 f e 17 16 nc nc 15 14 nc nc 13 12 nc nc 11 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc d 3 2 c b 1 isp 6 nc nc 5 4 nc nc 3 2 a nc 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 device nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc 5 b h 4 6 c nc 3 7 d e 2 8 g f 1 hv_prog 20 nc nc 19 18 nc nc 17 16 nc nc 15 14 nc nc 13 12 nc nc 11 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 device nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc
introduction page 20 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 devicesheet: attiny25, attiny45, attiny85 supported programming modes: isp , hvsp supported emulation modes: debugwire high voltage serial programming in system programming and debugwire emulation: vcc 6 a nc 5 4 g nc 3 2 nc nc 1 isp 6 e f 5 4 b d 3 2 a c 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 nc nc nc nc nc nc nc nc nc nc nc nc 5 b e 4 6 c nc 3 7 d nc 2 8 g f 1 vcc 6 a nc 5 4 nc nc 3 2 nc nc 1 hv_prog 20 h g 19 18 f e 17 16 nc nc 15 14 nc nc 13 12 nc nc 11 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc d 3 2 c b 1 isp 6 nc nc 5 4 nc nc 3 2 a nc 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 device nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc 5 b h 4 6 c nc 3 7 d e 2 8 g f 1
introduction page 21 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 attiny2313 devicesheet supported programming modes: isp , parallel programming supported emulation modes: debugwire in system programming and debugwire emulation vcc 6 a nc 5 4 g nc 3 2 nc nc 1 hv_prog 20 nc nc 19 18 nc nc 17 16 nc nc 15 14 nc nc 13 12 nc nc 11 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 isp 6 e f 5 4 b d 3 2 a c 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 device nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc 5 b e 4 6 c nc 3 7 d nc 2 8 g f 1 hv_prog 20 nc nc 19 18 nc nc 17 16 nc nc 15 14 nc nc 13 12 nc nc 11 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 isp 6 f e 5 4 d c 3 2 b a 1 jtag device nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc 11 nc f 10 12 nc nc 9 13 nc nc 8 14 nc nc 7 15 nc nc 6
introduction page 22 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 parallel programming devicesheet: atmega48, atmega88, atmega168 supported programming modes: isp , parallel programming supported emulation modes: debugwire in system programming and debugwire emulation vcc 6 b nc 5 4 g nc 3 2 nc nc 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 15 nc nc 6 16 nc nc 5 17 d nc 4 18 a nc 3 19 c nc 2 20 g e 1 vcc 6 u nc 5 4 nc nc 3 2 nc nc 1 hv_prog 20 t s 19 18 r q 17 16 nc o 15 14 n m 13 12 l k 11 10 j nc 9 8 h g 7 6 f e 5 4 d c 3 2 b a 1 isp 6 nc nc 5 4 nc nc 3 2 u nc 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 device nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc nc 11 o t 10 12 a n 9 13 b m 8 14 c l 7 15 d k 6 16 e q 5 17 f nc 4 18 g j 3 19 h nc 2 20 s r 1
introduction page 23 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 parallel programming vcc 6 b nc 5 4 g nc 3 2 nc nc 1 hv_prog 20 nc nc 19 18 nc nc 17 16 nc nc 15 14 nc nc 13 12 nc nc 11 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 isp 6 f e 5 4 d c 3 2 b a 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 device nc nc nc nc nc nc nc nc nc nc nc nc 15 nc nc 14 16 nc nc 13 17 d nc 12 18 a nc 11 19 c nc 10 20 nc nc 9 21 nc f 8 22 nc g 7 23 nc nc 6 24 nc nc 5 25 nc nc 4 26 nc nc 3 27 nc nc 2 28 nc e 1 vcc 6 u nc 5 4 nc nc 3 2 nc nc 1 hv_prog 20 t s 19 18 r q 17 16 p o 15 14 n m 13 12 l k 11 10 j i 9 8 h g 7 6 f e 5 4 d c 3 2 b a 1 isp 6 nc nc 5 4 nc nc 3 2 u nc 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 device nc nc nc nc nc nc nc nc nc nc nc nc 15 b a 14 16 c p 13 17 d o 12 18 e n 11 19 f nc 10 20 nc q 9 21 nc t 8 22 nc s 7 23 g m 6 24 h l 5 25 i k 4 26 nc j 3 27 nc nc 2 28 nc r 1
introduction page 24 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 devicesheet: atmega8 supported programming modes: isp , parallel programming supported emulation modes: debugwire in system programming and debugwire emulation vcc 6 nc nc 5 4 nc nc 3 2 nc nc 1 hv_prog 20 nc nc 19 18 nc nc 17 16 nc nc 15 14 nc nc 13 12 nc nc 11 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 isp 6 nc nc 5 4 nc nc 3 2 nc nc 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 device 21 nc nc 20 22 nc nc 19 23 nc nc 18 24 nc nc 17 25 nc nc 16 26 nc nc 15 27 nc nc 14 28 nc nc 13 29 nc nc 12 30 nc nc 11 31 nc nc 10 32 nc nc 9 33 nc nc 8 34 nc nc 7 35 nc nc 6 36 nc nc 5 37 nc nc 4 38 nc nc 3 39 nc nc 2 40 nc nc 1 hv_prog 20 nc nc 19 18 nc nc 17 16 nc nc 15 14 nc nc 13 12 nc nc 11 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 device nc nc nc nc nc nc nc nc nc nc nc nc 15 nc nc 14 16 nc nc 13 17 d nc 12
introduction page 25 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 parallel programming devicesheet: atmega16/32 supported programming modes: isp , pp , jtag prog supported emulation modes: jtag in system programming vcc 6 b nc 5 4 g nc 3 2 nc nc 1 2 nc nc 1 isp 6 f e 5 4 d c 3 2 b a 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 18 a nc 11 19 c nc 10 20 nc nc 9 21 nc f 8 22 nc g 7 23 nc nc 6 24 nc nc 5 25 nc nc 4 26 nc nc 3 27 nc nc 2 28 nc e 1 vcc 6 u nc 5 4 nc nc 3 2 nc nc 1 hv_prog 20 t s 19 18 r q 17 16 p o 15 14 n m 13 12 l k 11 10 j i 9 8 h g 7 6 f e 5 4 d c 3 2 b a 1 isp 6 nc nc 5 4 nc nc 3 2 u nc 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 device nc nc nc nc nc nc nc nc nc nc nc nc 15 b a 14 16 c p 13 17 d o 12 18 e n 11 19 f nc 10 20 nc q 9 21 nc t 8 22 nc s 7 23 g m 6 24 h l 5 25 i k 4 26 nc j 3 27 nc nc 2 28 nc r 1
introduction page 26 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 jtag programming and jtag emulation vcc 6 b nc 5 4 g nc 3 2 nc nc 1 hv_prog 20 nc nc 19 18 nc nc 17 16 nc nc 15 14 nc nc 13 12 nc nc 11 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 isp 6 f e 5 4 d c 3 2 b a 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 device 21 nc nc 20 22 nc nc 19 23 nc nc 18 24 nc nc 17 25 nc nc 16 26 nc nc 15 27 nc nc 14 28 nc nc 13 29 nc nc 12 30 nc f 11 31 nc g 10 32 nc e 9 33 nc c 8 34 nc a 7 35 nc d 6 36 nc nc 5 37 nc nc 4 38 nc nc 3 39 nc nc 2 40 nc nc 1 vcc 6 d h 5 4 i nc 3 2 nc nc 1 hv_prog 20 nc nc 19 18 nc nc 17 16 nc nc 15 14 nc nc 13 12 nc nc 11 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 isp 6 nc nc 5 4 nc nc 3 2 nc nc 1 jtag 10 h g 9 8 nc nc 7 6 f e 5 4 d c 3 2 b a 1 device 21 nc nc 20 22 nc nc 19 23 nc nc 18 24 a nc 17 25 e nc 16 26 c nc 15 27 g nc 14 28 nc nc 13 29 nc nc 12 30 nc b 11 31 nc i 10 32 nc f 9 33 nc nc 8 34 nc nc 7 35 nc nc 6 36 nc nc 5 37 nc nc 4 38 nc nc 3 39 nc nc 2 40 nc nc 1
introduction page 27 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 parallel programming off board targets avr with other than pdip package and or more than 4 0 pins will not fit on the avr dragon prototype area. all programming interface from avr dragon can through cables be connected to the off board target. note that pp/hvsp (parallel and high voltage serial programming) is not recommended to use off board the avr dragon. pp/hvsp signals are n ot level converted on the avr dragon. troubleshooting vcc 6 u nc 5 4 nc nc 3 2 nc nc 1 hv_prog 20 t s 19 18 r q 17 16 p o 15 14 n m 13 12 l k 11 10 j i 9 8 h g 7 6 f e 5 4 d c 3 2 b a 1 isp 6 nc nc 5 4 nc nc 3 2 u nc 1 jtag 10 nc nc 9 8 nc nc 7 6 nc nc 5 4 nc nc 3 2 nc nc 1 device 21 p o 20 22 nc n 19 23 nc m 18 24 nc l 17 25 nc k 16 26 nc j 15 27 nc nc 14 28 nc q 13 29 nc nc 12 30 nc t 11 31 nc s 10 32 nc r 9 33 nc h 8 34 nc g 7 35 nc f 6 36 nc e 5 37 nc d 4 38 nc c 3 39 nc b 2 40 i a 1
introduction page 28 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 known issues october 4th, 2006 in order to set isp frequency, avr dragon needs to sense target. see trouble shooting guide avr dragon requirements problem reason solution signature bytes read as 0x00 0x00 0x00 isp frequency is to high. lower isp freq under the board settings not able to communicate with device through debugwire reset pullup resistor to small remove or increase the pull-up value to 10k ohm or more. not able to communicate with device through debugwire decoupling capasitor destroys communication on reset line remove decoupling capasitor on reset line during debugwire emulation debugwire communication fails when using stk500 reset line strongly tied to vcc remove reset jumper on stk500 to allow avr dragon to control the line. after successfully enabling the dwen fuse, avr dragon is not able to enter debug mode reset line strongly tied to vcc remove reset jumper on stk500 to allow avr dragon to control the line. target voltage is read as 0v for onboard targets avr dragon get no reference voltage to the target voltage sensing. target voltage is sensed from either pin 2 on isp header or pin 4 on the jtag header. in order to get reference voltage to the level converters of avr dragon, connect pin 2 or 4 or 6 on the vcc header to pin 2 on the isp header. not able to set isp frequency avr dragon is not reading any target voltage. see above
introduction page 29 of 29 file://c:\documents and settings\administrator\...\ ~hh90c1.ht 2006-10-27 system unit physical dimensions................................ ...... ( h x w x d ) 53 x 105 x 15 mm power voltage requirements......................... .. 5.0v usb powered avr dragon current consumption................... 1 00ma max current source capability (to target)......... 300ma ambient temperature................................ .......0-70'c operation target voltage range............................... ........1.8 - 5.5 v i/o pins maximum pull-up on isp/jtag header........... 1k maximum pull-down on isp/jtag header...... 10k maximum source current vcc header........... up to total 300ma. note that the avr dragon requires a usb port that can d eliver up to 500ma. (self-powered usb hub) technical support before requesting techical support make sure you ha ve the latest available avr studio, tool firmware installed. the latest avr studio vers ion can be downloaded from www.atmel.com/avrstudio, and contains the latest fi rmware version for all atmel avr tools. when connecting your tool, avr studio will automati cally check the firmware version and request an update if needed. for technical support please contact avr@atmel.com. when requesting technical support for avr dragon please include the following informa tion: version number of avr studio. this can be found in avr studio menu "help->about" pc processor type and speed pc operating system and version what target avr device is used (complete part numbe r) fuse settings on the avr target clock frequency if clkpr (clock prescaler register) is used (for av rs with this feature) target voltage programming speed a detailed description of the problem, and how to r ecreate it. any error or waring information generated by avr st udio when the error occurred.

▲Up To Search▲

Price & Availability of ATAVRDRAGON

	To Download ATAVRDRAGON Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .